Providing user interface data on a mobile computing device

ABSTRACT

A system and a method are provided for managing network activation with a carrier and registration with a service provider. In one example, the method determines a network activation status. If the network is not activated, a utility is used to perform the activation. Further, the status of registration with a provider is determined. If not registered, a request is sent to a server of the service provider for a registration file configured to gather user registration information. The registration file is then received from the server. The registration file is executed on the personal computer. Data gathered by the registration file is then returned to the service provider&#39;s server to complete the registration procedures.

CROSS REFERENCE TO RELATED APPLICATION

This application is a divisional of U.S. application Ser. No. 11/218,346filed Aug. 31, 2005, which is a continuation of U.S. application Ser.No. 09/732,076 filed Dec. 7, 2000, both of which are herein incorporatedby reference in their entireties.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to wireless networks and, moreparticularly, to wireless network activation with carriers andregistration with service providers.

2. Discussion of Background

The wireless communication revolution is bringing fundamental changes todata networking and telecommunication, and is making integrated networksa reality. By freeing the user from the cord, personal communicationsnetworks, wireless local area networks (LAN's), and mobile radionetworks and cellular systems harbor the promise of fully distributedmobile computing and communications, any time, anywhere. Numerouswireless services are also maturing and are poised to change the way andscope of communication.

Many manufacturers have begun to incorporate wireless technologies intoa new kind of computer—the personal digital assistant (PDA). A PDA is acomputer that is small enough to be held in the hand of a user. A PDAruns personal information management applications such as an addressbook, a daily organizer, and electronic notepads. These applicationsmake people's lives easier.

FIG. 1 shows a basic configuration of a popular PDA brand, the Palm™ 10.However, the Palm™ 10 is much more than a simple PDA. This small, slim,device, about the size of your wallet, can hold 6000 addresses, 5 yearsof appointments, 1500 to-do items, 1500 memos, 200 e-mail messages, andcan run many different software applications.

The front panel of the Palm™ 10 is a large liquid crystal display(“LCD”) 11, which is touch-sensitive and allows a user to enter andmanipulate data. By using a stylus (not shown) to interact with thetouch-sensitive screen, a user may easily navigate through a host ofvarious software applications. A stylus is used to interact withinformation on a screen in much the same way a mouse is used with adesktop personal computer. The display device also includes a Graffiti™writing section 12 for tracing alphanumeric characters as input.

Regarding wireless connectivity, a given wireless network typically hasmany different carriers for the same network type. For example, BellSouth™ and Rogers AT&T™ are wireless carriers that both run Mobitex™networks. Further, many wireless computers are manufactured to becompatible with a particular network type, carrier, and/or serviceprovider.

Unfortunately, problems arise when a consumer, manufacturer, or providerlater desires the computer to be compatible with another network oranother carrier. Integrated within the computer's architecture, may bean operating system that allows a user to connect with a specificcarrier and/or service provider. For example, applications that allowconnectivity with a specific carrier, such as BellSouth™, may be writtento a read-only memory (ROM) of the PDA. Such a framework makes itdifficult to later make the PDA compatible with another carrier or withanother type of network.

The PDA that is compatible with only BellSouth™ can not be taken toEurope to be compatible with a French carrier, much less a wirelessnetwork in France. Thus, the manufacturer that builds the PDA that iscompatible with BellSouth™ will have to build a different PDA to becompatible with a French carrier, and another device for Australia, andanother for Japan, etc.

While a PDA may be manufactured for a regional carrier and/or serviceprovider, wireless networks naturally provide users with extendedcomputing capabilities and mobility. Users are able to move about,carrying their computers with them and maintaining uninterruptedcommunication with their servers. Wireless networks should be able toallow users to turn on their computers almost anywhere in the world, toestablish access to their home servers, and to retrieve their files andemail. Such mobility, however, is difficult with commonly availablewireless technology.

Consequently, the implementation of wireless networks presents newproblems. Unfortunately, classical communication theory and wirednetwork models does not efficiently solve these new problems.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be readily understood by the followingdetailed description in conjunction with the accompanying drawings. Tofacilitate this description, like reference numerals designate likestructural elements.

FIG. 1 shows a basic configuration of a popular PDA brand, the Palm™.

FIG. 2 is a block diagram of selected components of a computer thatincludes wireless network technology, in accordance with one embodimentof the present invention.

FIG. 3 is a block diagram of the architecture for the generic activationand registration framework (GARF), in accordance with one embodiment ofthe present invention.

FIG. 4 shows a high-level flowchart for a method of managing networkactivation with a carrier and registration with a service provider, inaccordance with one embodiment of the present invention.

FIG. 5A shows a more detailed flowchart for a method of managing networkactivation with a carrier and registration with a service provider, inaccordance with one embodiment of the present invention.

FIG. 5B is a continuation of the flowchart of FIG. 5A, in accordancewith one embodiment of the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

An invention is disclosed for a system and method for managing networkactivation with a carrier and registration with a service provider.Numerous specific details are set forth in order to provide a thoroughunderstanding of the present invention. It will be understood, however,to one skilled in the art, that the present invention may be practicedwithout some or all of these specific details.

General Overview

FIG. 2 is a block diagram of selected components of a computer 100 thatincludes wireless network technology, in accordance with one embodimentof the present invention. The computer 100 includes a processing device110, for executing applications and an operating system of the computer100, a memory device 120 for storing the operating system, data, andapplications (including plug-in executable files).

A display screen 130 is provided (preferably a touch sensitive screen)for display of operating system prompts, buttons, icons, applicationscreens, and other data, and for providing user inputs via tapping ortouching (or drawing in the Graffiti™ area) via a stylus or other touchmechanism. Hardware interface 135 connects to physical hard buttons andswitches located on a body of the computer 100 and provides signals toapplications running on the processing unit 110.

A bus 155 carries data and commands to/from the processing unit 110from/to other devices within the computer 100. For example, userapplications running on the computer 100 may be stored in the memorydevice 120. The user applications send application screens and otherdata outputs to display screen 130 for display via the bus 155. Userinputs (Graffiti™ area drawing, or tap selection, for example) aredetected by the screen 130 and sent to the processing unit 110 via thebus 155.

A mobile radio device 140 (part of the wireless technology in thecomputer 100) provides connectivity to a wireless network (not shown).The mobile radio device 140 is configured to detect inbound networktransactions from the network directed toward the mobile radio device140. For example, the inbound network transaction may be a pagenotification that is sent to a pager device executing on the processingunit 110.

In the embodiment of FIG. 2, the computer 100 is illustrated as apersonal digital assistant (PDA). A PDA is a handheld computer such as aPalm™, Palm III™, or Palm V™, or Palm VII™ organizers, manufactured byPalm, Inc. Other embodiments of the invention can include Windows CE™and Visor™ handheld computers, other handheld computers, other personaldigital assistants (PDAs), desktop computers, laptop computers,workstations, or mainframes.

The Palm™ and its operating environment are used herein to illustratevarious aspects of the present invention. However, it should beunderstood that the present invention may be practiced on other devices,including other Palm™ models, PDA's, computer devices, personalcomputers, notebooks, etc.

General Overview Of Generic Activation Framework

FIG. 3 is a block diagram of the architecture for the generic activationand registration framework (the “GARF”) 200, in accordance with oneembodiment of the present invention. The GARF is a system for providingnetwork activation and registration in a network that may have multiplecarriers and/or service providers.

The GARF 200 provides a driver device 202 that generally controlsnetwork activation and registration procedures for the computer 100.Networking applications that may be tailored for a specific carrier orservice provider are not included in the driver device. Rather, aplug-in device 204 (or multiple plug-in devices) may be installed in thecomputer 100. A plug-in device 204 includes hardware and/or softwarespecifically tailored for a particular carrier and service provider.Through a given plug-in device 204, the computer 100 can communicatewith a carrier and service provider that is intended for that plug-indevice 204. For example, a driver device 202 may communicate with aprovider's web server 206 with assistance from the plug-in device 204.Additionally, the provider's web server 206 can send a registration file208 to the driver device 202, which can then launch the registrationfile 208 in the computer 100. The registration file 208 is an executablefile configured to allow the computer 100 to be compatible with aparticular carrier and/or service provider.

The GARF 200 allows manufacturers to build a computer 100 for operationin wireless networks of any verbal language. For example, a genericdriver device 202 may be built that is nonspecific to any particularverbal language. The plug-in device 204, on the other hand, may be thenbe configured to be language specific. If France, for instance, hasthree different service providers that operate the same way in theFrench language, the GARF 200 allows one computer 100 to communicatewith all three service providers. In another embodiment, the plug-indevice 204 is generically built such that the computer 100 isgenerically operable in any wireless network of any verbal language.

Overview of Driver Device

The driver device 202 is hardware, software, or combination thereof,that is configured to manage procedures of the GARF 200. In oneembodiment, the driver device 202 includes an icon on the display screen130 for a user to select. Selection of the icon launches GARF 200procedures, including activating a wireless network with a carrier andhandling user registration with a service provider. BellSouth™, usedwith Palm VII™, is an example of a carrier. Palm.Net™, used with PalmVII™, is an example of a service provider. Palm.Net™ currently resellsBellSouth™ services for use with Palm VII™.

In one embodiment, the driver device 202 is an executable applicationthat a user will launch upon their first interaction with a wirelesscapable computer 100. The driver device 202 will drive the configurationof the computer 100 to obtain wireless connectivity, as well as performthe tasks required to obtain an account and/or identity with aparticular carrier and/or service provider. In one example, the driverdevice 202 may be launched by applications such as Clipper™ (used in thePalm™ operating system) when wireless connectivity has not yet beenestablished for the computer 100.

A feature of the GARF 200 is the ability for a user to step through anumber of screens in order to provide personal data to a wirelessservice provider, such as Palm.Net™. This setup process involves anumber of steps, including retrieving the appropriate screen(s),entering user information, submitting the information to the driverdevice, writing the personal data in memory, and submitting the data tothe service provider.

The driver device 202 is responsible for maintaining the system features(via the plug-in device 204). As an example, the Palm™ operating systemrequires certain system maintenance to ensure successful networktransactions with the carrier and service provider. The driver device202 accomplishes its tasks by launching a plug-in device 204 to activatethe network on the device (and to display location/carrier-specific userinterfaces and error messages). The driver device 202 can also call upona registration file 208, which in turn may be configured to executeregistration procedures on the computer 100. The driver device 202exposes and calls upon application program interfaces (API's) in boththe plug-in device and the registration file 208.

The driver device 202 is not tailored to a specific carrier and/orservice provider. Rather, the driver device 202 is generic to variouscarriers and/or service providers in a given wireless network. Forexample, the driver device 202 may be generally operable in all networksin France, but the internal components are not programmed to handlecommunications with one specific carrier and/or service provider. In oneembodiment, the driver device 202 is built into the memory device 120or, more specifically, into a read-only memory (ROM) portion of thememory device 120.

In one embodiment, communications from the provider's web server 206 tothe driver device 202 are handled in a protocol that includes HypertextTransfer Protocol (HTTP) over Transmission Control Protocol/InternetProtocol (TCP/IP). Communications from the driver device 202 to thecarrier are handled in a protocol that includes Hypertext TransferProtocol (HTTP) over Compressed Transfer Protocol (CTP), or thecarrier's own network protocol is used. Another embodiment handlescommunications with File Transfer Protocol (FTP) over TCP/IP. Othertypes of TCP/IP-based protocols may alternatively be used tocommunicate. The present invention is not limited to the specificprotocols disclosed herein.

In an alternative embodiment, deactivation of the carrier andde-registration of the service provider can occur. A computer 100 isdeactivated when the computer 100 is no longer enabled to communicate inthe wireless network. A computer 100 is de-registered when the computer100 no longer has an account with a service provider. Deactivation orde-registration can occur in at least the following two ways: someexternal process (outside of the computer 100) can be invoked to executedeactivation or de-registration; or the plug-in device 204 can beexplicitly prompted to execute deactivation or de-registration.

To deactivate/de-register a computer 100, the driver device 202 searchesthrough all plug-in devices 204 in the computer 100. If no plug-indevices 204 are found, deactivation is complete because without aplug-in device, a computer 100 is not network activated. In searchingfor plug-in devices 204, the computer 100 determines which networkplug-in device is responsible for deactivation. The driver device 202launches the found plug-in with a deactivation code. Note that thedeactivation code must be accompanied by appropriate parameters todenote the desired plug-in device for deactivation. If the plug-indevice also contains the service provider's registration (orde-registration) set of codes, the driver device 202 must determinewhether to launch the plug-in device 204 with a “de-register” codefirst. In one embodiment, the deactivation code is called by aregistration file 208 that is in the process of deactivating a componentof service.

Overview of Plug-in Device

The plug-in device 204 is hardware, software, or combination thereof,that allows the computer 100 to be compatible with a particular carrierand particular service provider. In a preferred embodiment, the plug-indevice 204 is an interface between software (e.g., wireless browserapplication) and hardware (e.g., mobile radio device 140) in thecomputer 100.

The plug-in device 204 may be configured to assist in establishingactivation and registration, by executing functions such as thefollowing: setting system features for the network activation uponresetting of the GARF 200; network activation/deactivation with aparticular carrier and registration/de-registration with a particularservice provider; maintenance of account identification for a particularcarrier and a particular service provider; and initiating appropriateuser interfaces during error conditions.

In a preferred embodiment, the plug-in device has the following twoprimary purposes upon launch by the driver device 202: (1) activate thecomputer 100 on a wireless network; and (2) register the computer 100with a service provider such as Palm.Net™, thereby allowing the computer100 to utilize the service provider's wireless services. The purpose ofthe GARF 200 is to perform common procedures in the wireless network.The plug-in device 204 is the component of the GARF 200 that containsdifferences for a particular mobile radio device 140, a particularcarrier, and a particular service provider, among other things. In oneembodiment, the plug-in device 204 is an executable file that is easilyinstallable into memory of the computer 100.

A plug-in device 204 is responsible for network activation andregistration, setting system features, and updating the memory state ofthe computer 100 according to the network being activate. In oneembodiment, the plug-in device 204 is tailored for a particular carrierand particular service provider. BellSouth™ is an example of a carrier.Palm.net™ is an example of a service provider. The carrier and serviceprovider, in turn, operate in a particular type of network. Mobitex™ isan example of a wireless packet data network. Other examples of anetwork include a cell phone network, a digital personal communicationsservice (PCS) network, and a global system for mobile communications(GSM) network. Thus, the plug-in is further configured to be compatiblewith the network in which the particular carrier operates.

As a secondary function, the plug-in device 204 provides error andwarning code user interfaces, which are tailored to a particular verballanguage (e.g., French, English, German, Spanish).

In another embodiment, the plug-in device 204 is designed to becompatible with multiple carriers and service providers in a givennetwork. For example, the plug-in device 204 may be multiplexed toreceive a call from the driver device 202, and the plug-in device 204may then switch between different carriers, depending on the call. Instill another embodiment, multiple, different plug-in devices 204 may beinstalled in the computer 100, for example, to allow the user to have achoice of various carriers and/or service providers. In yet anotherembodiment, a general plug-in device 204 is provided, for example, aplug-in device compatible with an English language wireless networkcovering all of North America. Alternatively, a more specific plug-indevice 204 may be installed to handle carriers and service providers,for example, in just the western United States.

Further, the different plug-in devices 204 may be configured to becompatible with each other. Regardless of the particular configurationof the plug-in devices 204, however, a plug-in device 204 is a componentthat can be readily redesigned after a computer 100 has beenmanufactured. Such flexibility of a plug-in device 204 is useful becausehardware and software components in a computer 100 may be entrenchedwithin the computer's operating system (e.g., the ROM). Thus, theplug-in device 204 provides a component for the computer 100 thatfacilitates changing the computer's compatibility for different carriersand/or service providers.

Regarding commands that the driver device 202 sends to the plug-indevice 204, a plug-in device 204 is preferably designed to handlecertain predefined launch codes from the driver device 202. Table 1below contains examples of launch codes that may be used in the Palm™operating system.

TABLE 1 Examples Of Launch Codes That Driver Device 202 May Include In ACommand Sent To Plug-In Device 204 PLUGIN_TYPE Return a wireless networkor service provider, or both to the caller-noting the type of plug-inWN_RESET Set any system features needed for network stack of devicerelease SP_RESET Set any system features needed for service providerCK_WN_ACTIVATE Check system feature and memory values (when systemfeatures may not be correct) to determine (true or false) if thewireless network is active WN_ACTIVATE Configure a device so that it isable to effectively communicate on the network WN_DEACTIVATE Perform awireless network deactivation CK_SP_REGISTER Check system features anddatabase entries (when system features may not be correct) to determine(true or false) if the service provider has been registered with. If theservice provider has not been successfully registered with, this callwill return false, with an optional parameter of a URL. The URL can thenbe used by the driver to retrieve a registration file 208. SP_DEACTIVATERemove any system features, database entries, or flash values utilizedby the service provider to denote successful registration. SP_COMPLETEPerform any service-provider-centric flash/system feature/database entryactivity that denotes the FINAL step of activation and registrationSP_FAIL Perform any service-provider-specific cleanup activity that mustbe performed to return the state of the device to normal

Overview of Auxiliary Screen Flow

In order to create and provision accounts with a given service provider,the service provider most-likely wants to collect data about the user.Such data may include name, address, account identifier, password, etc.

The auxiliary screen flow of the GARF 200 involves downloading andexecuting a registration file 208 from the provider's web server 206. Aregistration file 208 is preferably an executable file configured to beexecuted as-is on the computer 100. (In the Palms operating system, anexecutable file is commonly referred to as a “PRC”.) The registrationfile 208 renders a set of dialogs (or “screens”) to collect userregistration data. The registration file has a calling convention and anexpected set of results. The driver device 202 can then controlprocedures to set up the account for the user.

In other words, in order to collect user information for serviceprovider registration, the driver device 202 has the ability todynamically query (i.e., download) a server of the provider for theregistration file 208. The registration file 208 is preferably kept asminimal in size as possible so as not to unduly delay the user'sexperience. As an example, the plug-in device sends a uniform resourcelocator (URL), or address, to the driver device 202. The driver device202 in turn sends a request to the provider's web server 206 to retrievethe registration file 208 located at the URL. Once retrieved, theregistration file 208 may be executed on the computer 100 to collectuser registration data. In one embodiment, execution of the registrationfile 208 involves communicating directly with the web, without firstgoing through the driver device 202.

The registration file 208 should be a temporary executable fileconfigured to delete itself after its operations have been performed(i.e., after registration is complete). The registration file 208 shouldexit execution successfully (or with a failure error) directly to thedriver device 202, so that any cleaning-up or processing by the computer100 may resume. In other words, the registration file 208 should notleave the computer 100 in an unstable state. In one embodiment, theregistration file 208 uses Compressed Transfer Protocol (CTP) calls. Theregistration file 208 may be configured to utilize error and warninguser interfaces contained within the plug-in device 204. In a preferredembodiment, the registration file 208 is configured to utilize error andwarning user interfaces contained within the registration file 208itself.

The registration file 208 can be configured dynamically by the serviceprovider. For example, if the service provider changes its rate plan,the registration file 208 can readily be changed to accommodate the newrate plan. The new rate plan can then be displayed to the user when theregistration file 208 is downloaded and executed on the computer 100.Note that the registration file 208 resides outside of computer 100 (atprovider's web server 206, for example) before the registration file 208is downloaded and executed by the driver device 202.

Overview of Provider's Web Server

In a preferred embodiment, the provider's web server 206 is accessiblevia a communication network. Examples of a communication network includea local area network (LAN), a wide area network (WAN), the globalpacket-switched network known as the “Internet” or the “World Wide Web”(web) . The web server 206 provides the registration files 208 of theauxiliary screen flow, as well as any other logic to be used from withinthe executable file. In one example, the provider's web server 206 isaccessible via the Internet through Palm™ Web Clipping Proxy Servers.HTTP is the proxiable protocol handled by Web Clipping Proxy Servers.

As discussed above with reference to the auxiliary screen flow, theplug-in device 204 may return a URL to the driver device 202. The URL isthen sent as a request to the provider's web server 206. That URLreturns one static registration file 208 for the auxiliary screen flow.

Accordingly, the service provider preferably carves some space from itsfile system directory to store the screens for the execution of theregistration file 208.

Process Overview

FIG. 4 shows a high-level flowchart for a method of managing networkactivation with a carrier and registration with a service provider, inaccordance with one embodiment of the present invention. The methodstarts in step 301 where a network activation status is determined. Itmay be determined, for example, that a wireless network for the mobileradio device 140 is enabled, but the computer 100 is not activated witha carrier. In such a case, the computer 100 will perform networkactivation procedures in step 302.

In step 303, registration status with a service provider is determined.If the computer 100 is not registered, a request will be sent to aserver of a service provider in step 304. This request preferablycontains an address to a registration file 208 configured to gather userregistration information. The registration file is received from theserver in step 306. In step 308, the registration file 208 is executedon the computer 100. Execution of the registration file 208 involvesgathering registration information from the user. In an anotherembodiment, the method further includes returning the gathered data tothe server to complete network activation.

In one embodiment, the method steps of FIG. 4 are managed by the driverdevice 202. As discussed above with reference to FIG. 3, the driverdevice will drive the configuration process to obtain wireless networkactivation, as well as perform the tasks required to obtain an accountand/or identity with a particular service provider.

FIG. 5A and FIG. 5B, collectively, show a more detailed flowchart for amethod of managing network activation with a carrier and registrationwith a service provider, in accordance with one embodiment of thepresent invention. The method starts in step 402 where a driver device202 in the computer 100 is launched. For example, the driver device 202may include a user-selectable icon on the display screen 130 of thecomputer 100, as discussed above with reference to FIG. 3. Uponselection of the icon, the driver device 202 is launched, therebystarting procedures of the GARF 200.

In step 404, the plug-in device 204 is launched to check for networkactivation with a carrier. As discussed above with reference to FIG. 3,the computer 100 may contain multiple, different plug-in devices 204. Ina preferred embodiment, the driver device 202 scans for all of theplug-in devices 204 by searching the computer 100 for devices that matcha particular file type. Accordingly, when a plug-in device 204 isdesigned, the plug-in device 204 should be designed to match apredetermined type that is searchable by the driver device 202. In oneembodiment, the driver device 202 makes a call to each and every plug-indevice 204 and checks for network activation in each.

As an example of step 404, the driver device 202 sends a “check wirelessnetwork activation” command (e.g., CK_WN_ACTIVATE) to a plug-in device204 that has information on whether the computer 100 is networkactivated. “Network activated” means that the computer is capable ofcommunicating in the network (e.g., Mobitex™) provided by the carrier(e.g., BellSouth™). Accordingly, a given wireless network can havemultiple, different carriers operating in the given wireless networktype. In a preferred embodiment, the computer 100 is manufactured to benetwork activated by having the mobile radio device 140 and appropriatenetwork components built into the operating system of the computer 100.If the computer 100 is not network activated, a plug-in device 204 islaunched in step 405 to activate the network with the computer 100. Thelaunched plug-in device handles the activation process. If networkactivation fails, an error is returned to the driver device 202, anappropriate error message is displayed, and the method is done.

Assuming the computer 100 is appropriately network activated, a plug-indevice 204 is launched to check for registration with a service providerin step 406. “Device” registration means that the computer 100 has anaccount with a service provider in the wireless network. In analternative embodiment, “user” registration means that the user of thecomputer 100 has an account with the service provider. In anotherembodiment, both the device and the user may be registered with theservice provider, and the account with the service provider containsinformation specific to both the user and the particular device (i.e.,computer 100). In this description, “device” registration and “user”registration may be used interchangeably to refer generally to accountregistration with a service provider.

In decision operation 408, it is determined if the device is registeredwith a service provider. In other words, it is determined if an accountexists with a service provider in the given wireless network. If thedevice is registered, a plug-in device is launched in step 410 with anerror to indicate the device is already registered. For example, adialog screen (e.g., “Already Activated”) is displayed to indicate tothe user that the computer 100 has previously been registered withPalm.Net™.

However, if the device is not registered, an address to a registrationfile 208 is received from the plug-in device 204 in step 412. Forexample, the plug-in device 204 may have a URL for a registration file208, as discussed above with reference to FIG. 3. In one embodiment,this registration file 208 is located on a provider's web server 206.The registration file 208 is an executable file configured to gatherregistration information from the user. The plug-in device 204 sends theregistration file's URL to the driver device 202 upon determining thatthe computer 100 is not registered with the particular service provider.

In step 414, a request is sent to a server of the service provider forthe registration file 208. For example, as discussed above withreference to FIG. 3, the driver device 202 sends an HTTP request to aweb server of the service provider. The HTTP request includes theregistration file's URL. Communications with the provider's web server206 may include procedures for encrypting data, connecting with the webserver, and sending the URL to the web server. Information that may beimbedded in the URL includes the following: carrier identification, thetype of verbal language (e.g., English or French) in which the computer100 is operating, screen resolution of the display screen 130, and otherenvironmental information of the computer 100.

In step 416, the registration file 208 is received from the server. Forexample, upon receiving the HTTP request from the driver device 202, theweb server directs the registration file 208 to be returned to thecomputer 100.

The method continues in FIG. 5B with launching the registration file 208in step 418. For example, as discussed above with reference to FIG. 3,an auxiliary screen flow is downloaded from the web and is executed onthe computer 100. Launching the registration file starts in decisionoperation 420, where it is determined if an account is to be setup withthe particular service provider. For example, the registration file 208displays a dialog on the display screen 130 to query the user if anaccount is to be setup. If an account is not to be setup, a “Cancel”screen is displayed in step 422 and the method is done. For example, theuser may select a “Cancel” icon that initiates cancellation proceduresof the registration process.

If an account is to be setup, registration information is then receivedfrom the user in step 424. For example, dialog screens are displayedduring execution of the registration file 208 for the user to respond toregistration queries. These dialog screens may query the user for someof the following information: username, alternative username, password,password question, password answer, first name, last name, emailaddress, gender, birthday, and mailing address. The computer 100receives the corresponding user-inputted information.

After user registration is received, it is determined in decisionoperation 426 if registration is to be confirmed or cancelled. Forexample, a dialog screen appears to query the user of whether to“confirm” or to “cancel” the registration process with the serviceprovider. If registration is to be cancelled, the registration processis ceased and control is returned to the driver device 202 in step 440.

However, if registration is to be confirmed, the data gathered by theregistration file 208 in step 424 is returned to the provider's webserver 206 to complete network registration in step 428. For example,the registration file 208 sends the gathered account data to the driverdevice 202, which in turn sends the gathered account data to theprovider's web server 206.

In decision operation 430, it is determined if registration isacceptable to the service provider. For example, upon receiving theaccount data, the service provider responds in approval or denial ofregistration. Registration may be unacceptable for the followingreasons: insufficient information (e.g., no username provided by theuser), or invalid information (e.g., a password that is too short or ausername that is already in existence) . If registration is notacceptable, an “Error” screen is displayed in step 436. The user will bequeried whether to retry. If the user does not want to retryregistration, control is returned to the driver device 202 in step 440.However, if the user does want to retry, the method returns to step 418where the registration file 208 is reset and launched.

On the other hand, if registration is acceptable, a “Done” screen isdisplayed in step 432. For example, the registration file 208 launchesthe done screen to indicate to the user that registration is acceptableand confirmed with the service provider. In step 434, a useridentification is received from the provider's web server 206. Forexample, the web server returns an identification code that uniquelyidentifies the computer 100 and/or the user for future logons with theservice provider.

In one example, the identification code is accompanied by an HTTP cookiefor the computer 100 to store in a cookie jar in the computer 100. AnHTTP cookie, in this context, is a text file that contains registrationinformation necessary for logons with the service provider. A cookie jaris a memory location in the computer 100 for storing HTTP cookies. TheHTTP cookie may be retrieved from the cookie jar during future logons.The HTTP cookie will allow for quick and easy logons, that is, when theuser logs onto the same service provider using the same computer 100.

If for some reason the user identification is not properly received fromthe provider's web server 206, error messages are displayed and thecomputer 100 retries to get the user identification from the provider'sweb server 206.

In step 440, control of network setup procedures is returned to thedriver device 202. Success or failure parameters from the registrationprocess are also returned to the driver device 202. Registrationcompletion operations are then performed in step 442. For example, thedriver device 202 may send success commands to a plug-in device 204,which will in turn initiate displaying of successful completion screens.Alternatively, the driver device 202 may send failure commands to aplug-in device 204, which will in turn initiate displaying ofcancellation screens. Upon performing the completion operations, themethod is then done.

System And Method Implementation

Portions of the present invention may be conveniently implemented usinga conventional general purpose or a specialized digital computer ormicroprocessor programmed according to the teachings of the presentdisclosure, as will be apparent to those skilled in the computer art.

Appropriate software coding can readily be prepared by skilledprogrammers based on the teachings of the present disclosure, as will beapparent to those skilled in the software art. The invention may also beimplemented by the preparation of application specific integratedcircuits or by interconnecting an appropriate network of conventionalcomponent circuits, as will be readily apparent to those skilled in theart.

The present invention includes a computer program product which is astorage medium (media) having instructions stored thereon/in which canbe used to control, or cause, a computer to perform any of the processesof the present invention. The storage medium can include, but is notlimited to, any type of disk including floppy disks, mini disks (MD's),optical discs, DVD, CD-ROMS, micro-drive, and magneto-optical disks,ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices(including flash cards), magnetic or optical cards, nanosystems(including molecular memory ICs), RAID devices, remote datastorage/archive/warehousing, or any type of media or device suitable forstoring instructions and/or data.

Stored on any one of the computer readable medium (media), the presentinvention includes software for controlling both the hardware of thegeneral purpose/specialized computer or microprocessor, and for enablingthe computer or microprocessor to interact with a human user or othermechanism utilizing the results of the present invention. Such softwaremay include, but is not limited to, device drivers, operating systems,and user applications. Ultimately, such computer readable media furtherincludes software for performing the present invention, as describedabove.

Included in the programming (software) of the general/specializedcomputer or microprocessor are software modules for implementing theteachings of the present invention, including, but not limited to,identifying plug-in devices, requesting registration file downloads,launching registration processes, and transferring registration data toservice providers, according to processes of the present invention.

In the foregoing specification, the invention has been described withreference to specific embodiments thereof. It will, however, be evidentthat various modifications and changes may be made thereto withoutdeparting from the broader spirit and scope of the invention. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

1-29. (canceled)
 30. A mobile computing device, comprising: a read-only memory comprising network settings for at least one wireless carrier; and a processing device configured to provide user interface data to the read-only memory after the mobile computing device has been manufactured.
 31. The mobile computing device of claim 30, wherein the processing device comprises a plug-in device configured to provide the user interface data to the read-only memory.
 32. The mobile computing device of claim 31, wherein the plug-in device comprises hardware.
 33. The mobile computing device of claim 30, wherein the processing device comprises an operating system comprising the user interface data.
 34. The mobile computing device of claim 30, wherein the processing device comprises an executable file comprising the user interface data.
 35. The mobile computing device of claim 30, wherein the user interface data is specific to the at least one wireless carrier.
 36. The mobile computing device of claim 30, wherein the read-only memory is configured to store network settings for a plurality of wireless carriers, wherein the processing device is configured to obtain network settings for a particular carrier from the read-only memory based on an account ID and to activate the mobile computing device with the carrier based on the network settings and the ID.
 37. The mobile computing device of claim 36, wherein the processing device is configured to display a carrier-specific user interface based on a particular carrier associated with the account ID. 